Thank you for your contribution! 🙏 We will review it as soon as possible.

Hey Tom, we are in need of a release to address some CVEs. A major release will be tough to get to, since I need some time to extensively test my batch scraping PR. Is there any chance you can cut a minor release?

I think this should be mergable once you get the resource discovery test fix from master. It'd be great if you can cut a minor release with this and the .NET version bump: #2517

My thought is to create two releases. A minor one with just the version bumps, and a major one with this batch scraping PR: #2459 afterwards. Just in case things go wrong on the later :)

My thought is to create two releases. A minor one with just the version bumps, and a major one with this batch scraping PR: #2459 afterwards. Just in case things go wrong on the later :)

Given Batch is already merged, this is going to be more painful to do a patch so let's just roll forward in case of an issue.

/azp run Promitor CI - Scraper Agent

@tomkerkhove you need to re-run these pipelines a few more times if you want to have them all passing. We got throttled on Resource Discovery Agent, and Scraper Agent is failing due to flaky OTEL Collector tests. Let me know if you want help on this.

@hkfgo Sadly they have been failing more than passing (did not get it to pass after 3-4 runs even) since we added batch support.

Can you please have a look what is up?

/azp run Promitor CI - Scraper Agent

Well, I've filed an issue here already: #2553. I think collector tests became flaky recently. Unlikely due to how tests themselves are written I'm guessing, but rather how the underlying test components are set up? It'd definitely save a lot of headache to get that resolved, but for now I think we just have to re-run CI multiple times.

I don't think I have the privilege to re-run CI here; I'm guessing CI on someone else's PR can only re-run by that person or the maintainer? I'll try to open a separate PR then

I seemed to get a clean PR here but that's because the Azure Devops steps never actually ran :/ I tried troubleshooting for a few hrs but no luck, those pipelines never got triggered even though they should based on config. (sorry about all those junk PRs for testing btw). I think there are a few options we can take right now:

1. Hand me the privilege to re-run pipeline steps, if you don't mind.
2. Alternatively, re-run the pipelines yourself; it'll take a few tries but they'll turn green I believe.
3. Merge the code with that one broken CI step. Yuck I know but the flakiness should be fixable in the future.

Let me know what you think? Thanks!